Basic TA Configuration

Before you run TA, you should customize its configuration to suit your organization's needs. You can add or adjust production schedule parameters, mail configuration, default job properties, security restrictions, and other details. One of TA’s many strengths is its flexible architecture.

During the installation of TA, one user account is created containing the installer’s user name. The user record includes a security policy and a list of the TA functions available to you. By default, this account is considered the TA Administrator/Super User and can perform all functions.

The basic configuration is complete when you have finished adding users. Advanced configuration options include creating and editing security policies, setting logging options, and creating queues and agent lists. The Tidal Automation User Guide contains detailed information about using and configuring TA.

You can configure most properties of the Master using the System Configuration dialog in the TA Web Client. Other major Master parameters are managed through the master.props file on the Master machine as described in this chapter:

Note: Ensure that the regional settings used by the TA Web Clients are the same as those used on the Window Master. Different regional settings may use other formatting for dates and times. If the Master is not using the same regional settings, alerts and job activity may not operate correctly.

Configuring the TA System

Before using TA, configure the Master operation parameters, job defaults, mail system connections (if you use email), and job status sort order.

To configure the TA system:

  1. Launch the TA Web Client. Go to http://<servername>:8080/client and log on using install Super User’s network credentials.

  1. Click System Configuration on the Activities menu. The System Configuration dialog is displayed.

    Note: Refer to the Getting Started chapter in the Tidal Automation User Guide for more information on the options in the System Configuration dialog.

Database Connection Pool Configuration

The number of database connections on the Master needs to match the expected load of the system. If the number of database connections is set to 2 on the Master and the number of sync threads is set to 12 on the TA Web Client, there will be 12 simultaneous threads spawned on the Master competing for 2 database connections. Depending on the duration of time the 2 connections are held, there can be potential scenarios when one or more of these Master threads will fail to process sync requests as it will fail to get a database connection. Hence, it is important to set the number of database connections on the Master to facilitate regular Master processing and the sync-up process. If the TA Web Client has 12 sync threads, the connections on the Master should be slightly higher than 12. The number of database connections can be set using the DatabaseConnections setting in master.props.

Authenticating LDAP Users to Connect to the SQL Server Database

You can authenticate LDAP users to connect to the Microsoft SQL Server database from the TA Master and the Client Manager.

To authenticate LDAP users to connect to the Microsoft SQL Server database:

  1. Download the Microsoft JDBC driver for SQL Server from Download Microsoft JDBC Driver for SQL.

  2. Create a domain user from the Microsoft SQL Server database server under Security > Logins and Databases > Tidal Admiral database > Security > Users. Here, the Tidal Admiral database is the name of Microsoft SQL Server.

  3. In the master.props file

    • Add these values to the JdbcURL parameter:

      integratedSecurity=true;trustServerCertificate=true;
    • Add the library to the Classpath parameter:

      C:\mylib\mssql-jdbc-<download version>.jre8.jar. 

      Example: Here, <download version> refers to the latest version of the JDBC driver downloaded at step 1.

    • Add this path to the JVMARGS parameter:

      -Djava.library.path=C:\mylib.
    • Add the mssql-jdbc_auth-<download version>.x64.dll file to the system path or in a directory such as C:\mylib. Here, <download version> refers to the latest version of the JDBC driver downloaded at step 1.

  1. In the clientmgr.props file

    • Add this path to the JVMARGS parameter:

       -Djava.library.path=C:\mylib
    • Add the C:\mylib\mssql-jdbc-<download version>.jre8.jar file to the TA Client Manager’s \lib folder.

      Example: Here, <download version> refers to the latest version of the JDBC driver downloaded at step 1

  1. Add the values to the MasterCacheJdbcURL parameter in the tes-6.0.dsp file:

    integratedSecurity=true;trustServerCertificate=true;
  2. Configure the TA Master to start with the domain user created in Step 2.

  3. Configure the Client Manager to start with the domain user created in Step 2.